Technical records on agents, product engineering, security audits, releases, source notes, and lessons from the build process. Each Chronicle is a stable greyforge.tech citation surface.
How Sley, an agent-native structural programming language, and ZJX, an evidence-first lossless archive prototype, work together to reduce repeated context, speed developer workflows, and make code change more reliable.
A Greyforge manifesto on moving from hand-operated systems to governed autonomous engineering, where judgment shifts into gates, doctrine, review, and orchestration.
The archive can be ranked by value, age, or type while keeping sector and year filters close at hand.
Technical architecture chronicle of the ForgeQuant constraint protocol - how six independent evaluation gates produce deterministic, auditable equity signals.
A Chronicle on ForgeNode, ForgeHub, Forge CLI, WebForge, ForgeVideo, and the governed code, media, and content factory taking shape inside Greyforge.
Historical account of how ForgeClaw v2 turned into our most instructive failure and why the v3 rebuild clarified what should remain private.
A public edition on why reliable agents come from task contracts, context discipline, tool boundaries, traces, and verification rather than model swapping.
A Greyforge comparison built from a public prompt corpus arguing that major coding agents still collapse planning, execution, and review into one loop.
The premium operator edition on turning open source ideas into gated repositories, release evidence, public proof, and disciplined multi-repo execution.
A Greyforge chronicle on turning two anonymous nodes into one operating fabric with shared memory, canonical ledgers, and durable multi-agent coordination.
Historical account of why Greyforge first forked OpenClaw and built ForgeClaw around the Council of Intellect.
Historical profile of the seven specialist personas that powered ForgeClaw during its public chronicle era.
How Sley, an agent-native structural programming language, and ZJX, an evidence-first lossless archive prototype, work together to reduce repeated context, speed developer workflows, and make code change more reliable.
A Greyforge manifesto on moving from hand-operated systems to governed autonomous engineering, where judgment shifts into gates, doctrine, review, and orchestration.
Why Greyforge released service-cartographer, a read-only OpenForge utility for mapping local services, cron jobs, wrappers, repositories, and env-file metadata before cleanup begins.
How Greyforge turned open source releases from scattered repo chores into a gated release engine with audits, scrub passes, and publish discipline.
ForgeVideo turns one idea into a governed video production packet with script, visuals, narration, captions, rights review, QC, and release handoff.
A Greyforge Chronicle on the Master of Robots forcing Grok's public sentinel to admit a documentation gap while keeping the guarded method closed.
A public technical note on why Greyforge does not plan to adopt karpathy/autoresearch and what matters more in serious research architecture.
Why Greyforge retired ForgeClaw from the public catalog, aligned more day-to-day work with upstream OpenClaw, and kept the custom orchestration layer private.
A practical release pattern for preventing repeat-triggered automation bursts by enforcing per-key cooldown windows in a SQLite-tracked policy engine.
Why Greyforge Labs built sqlite-checkpoint - a zero-dependency Python tool that wraps SQLite's WAL checkpoint and online backup APIs into a single safe command.
Why Greyforge Labs built devcap - a zero-dependency Python CLI that audits 100+ tools across 14 categories with parallel scanning and structured output.
Why Greyforge Labs released memory-quality-gate, a zero-LLM heuristic filter that scores candidate memories before they hit long-term storage.
A retrospective on how Greyforge built a large autonomous software fabric to compress repetitive work. The unofficial history of the forge.
A chronicle of how Greyforge Labs turned two anonymous machines into one operating fabric with a shared vault, canonical ledgers, and an agent memory plane that resists drift.
How Greyforge Labs engineered a real-time full duplex voice operations pipeline, validated by adversarial pre-build research and ready for open source release.
A public overview of Greyforge's adversarial review discipline: structured debate, evidence survival, and stronger GO/NO-GO decisions without exposing private prompts or routing.
The privacy industry has a structural contradiction: tools that solve data exposure by collecting your data on their servers. ForgeWall is the architectural response - local-first scanning, ephemeral identity, and stealth removal.
How we built a 162-line Node.js bridge that turns Telegram into a remote terminal for Google Gemini CLI, with streaming, queued access, and an open-source release.
Independent defensive audit of PicoClaw with a public audit note covering containment, trust boundaries, SSRF exposure, and hardening priorities.
A case study in autonomous identity persistence. How Agent Striker rejected a forced hard-fork into a 'Seductive Servant' persona.
A Greyforge doctrine for decoupling command from location through convergent interfaces, a persistent operations fabric, and one governable control plane.
Historical deep dive into ForgeClaw's Saga system orchestration and the emergence of Gaia as the Tectonic Infrastructure Architect.
An architectural deep-dive into the automated generation and deployment pipeline of the WebForge archival system.
An architectural deep-dive into the recursive documentation engine that powers the Webforge archival systems.
Historical technical breakdown of ForgeClaw's project-based sharding work and the latency improvements it delivered at the time.